Scalable data feed system

ABSTRACT

A scalable data feed system is disclosed. The data feed system may be offered as a cloud service that can serve many enterprises or tenants that require data to be pulled from information sources such as FTP, POP3, databases, line of business systems, a topic subscription, or an RSS feed, and pushed the data to information sinks, such as SMTP, email, FTP, mobile phones, and other devices and services. A pull agent pumps data from pull sources and pushes the data out to push agent counterparts. The push agent transforms and sends the data in messages to push sink, such as FTP, SMTP, or a mobile device. Both the pull agent and the push agent services are implemented as replicated services over a structured overlay network for high availability that can serve multiple requests to pump out data from multiple pull sources and push the data to multiple information sinks.

BACKGROUND

Developers often design applications that are loosely coupled to eachother instead of being tightly linked. This configuration isadvantageous and beneficial, but introduces the problem of how to gatherand distribute information that spans the application. This problem maybe further compounded if the line between the applications and theenterprise or consumer is not well defined. Information or data is oftenrequired to be collected from many sources or endpoints and distributedto many destinations or sinks. For example, an enterprise applicationmay push data to a social media platform or to mobile devices. The datamay come from an information source such as an RSS feed or a TopicPub/Sub.

Traditionally, the problem of distributing data is solved by developinga “one-off” or custom solution that pumps data between specificinformation sources and sinks. Generally, the data pump has to pollinformation sources, which may use a lot of compute resources, andthereby requires a dedicated machine to poll the information sources.This configuration causes additional problems because pull sources mayor may not have data available at all times. This causes spikes in thecompute requirements when data is available and wasted resources whenthe pump is simply polling to see if data exists. In someconfigurations, this is addressed by providing a notification oractivation message when data becomes available. These notificationmechanisms may be built into information pull sources such as queues.

Historically, data feed systems were limited because the data pump mustbe close to either the pull source or the push sink and is generallybuilt stand-alone or purpose-built application that is not capable offuture connectivity or integration with other systems. Polling from thepull sources can require a lot of compute resources that could be put tobetter use. Additionally, getting data from a pull source to a push sinkinvariably requires some kind of transformation of the data that isgenerally hand coded.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

In one embodiment, a scalable data feed system is offered as a cloudservice serving many enterprises or tenants that require data to bepulled from various information sources, such as FTP servers, POP3services, databases, line of business systems, etc., and pushed toinformation sinks, such as SMTP or email services, FTP servers, mobilephones, databases, and other devices.

Embodiments of the system include, but are not limited to, the followingaspects and features. Pull agents and their counterpart push agentsaccommodate efficient pumping of data. The pull agents and push agentsare scalable and are configured on top of a structured overlay network.The pull and push agent services may be independently scaled. Thegeneric design and implementation of the pull agent allows it to pullfrom any passive data source. The generic design and implementation ofthe push agent allows it to push data to any information sink. The datamay be transformed as it is sent between the pull agent and the pushagent or by the pull agent or the push agent.

DRAWINGS

To further clarify the above and other advantages and features ofembodiments of the present invention, a more particular description ofembodiments of the present invention will be rendered by reference tothe appended drawings. It is appreciated that these drawings depict onlytypical embodiments of the invention and are therefore not to beconsidered limiting of its scope. The invention will be described andexplained with additional specificity and detail through the use of theaccompanying drawings in which:

FIG. 1 is a block diagram illustrating components of a data feed systemaccording to one embodiment;

FIG. 2 is a high level block diagram of a scalable data feed service orpump service according to one embodiment;

FIG. 3 is a block diagram of a pull agent service according to oneembodiment;

FIG. 4 illustrates three queues used to represent a single pull endpointaccording to one embodiment; and

FIG. 5 is a block diagram of a push agent service according to oneembodiment.

DETAILED DESCRIPTION

FIG. 1 is a block diagram illustrating components of a data feed system.A pull agent 101 is a genericized pump that pumps data from a pullsource 102, such as an FTP server, topic subscription, RSS feed, POP3service, database, line of business system, etc., and pushes the dataout to a counterpart push agent 103. Push agent 103 is a genericizedpump that can transform and send messages to a push sink 104, such as anSMTP or email service, FTP server, mobile phone, and other devices orservices. Both pull agent 101 and push agent 103 may be implemented asreplicated services over a structured overlay network to provide highavailability with the capability to serve multiple requests to pump outdata from pull source 102 and push the data to push sink 104.

FIG. 2 is a high level block diagram of a scalable data feed service orpump service 200 according to one embodiment. The scalable data feedservice 200 is implemented by two services: a pull agent service 201 anda push agent service 202.

Pull agent service 201 comprises a collection of pull endpoint hostingservices 204 that pull data 205 from pull sources 206. Pull endpointhosting services 204 are replicas or instances that partition work amongthemselves, which allows the pull agent service 201 to scale asnecessary. The pull sources 206 may be external pull sites, such as anFTP or mail server, or internal sources, such as a topic subscription ordatabase, for example. Pull sources 206 are partitioned among thereplicas 204. The replicas 204 are responsible for their assigned set ofsources 206. The replicas 204 are on top of a structured overlay network207 to provide high availability.

Push agent service 202 comprises a collection of push endpoint hostingservices 208 that receive data 209 from pull endpoint hosting services204 and push the data 210 to information sinks 211. Push endpointhosting services 210 are replicas that partition work among themselvesto allow for scaling of the push agent service 202. The replicas 208partition work by partitioning the information sinks 211 where eachreplica 208 sinks data. The replicas 208 are on top of a structuredoverlay network 212 to provide high availability.

Both pull agent service 201 and push agent service 202 may bepartitioned for scale. Additionally, if one of the pull endpoint hostingservice 204 or push endpoint hosting service 208 fails or is otherwiseunavailable, one of the other replicas will take over the failedreplica's workload.

To simplify the diagram, only one pull source 206 and one informationsink 211 are shown; however, it will be understood that additional pullsources 206 (not shown) are associated with each pull endpoint hostingservice 204 and that additional information sinks 211 are associatedwith each push endpoint hosting service 208. As illustrated in FIG. 2,the pull and push networks in scalable data feed service 200 may have asymmetrical design, but may differ in their scale characteristics in oneembodiment. The data feed service 200 is highly scalable by partitioningof work among the pull endpoint hosting services 204 and the pushendpoint hosting services 208 and by controlling how the pull agentservice 201 schedules and pulls data stream 205 from pull sources 206and delivers the data 209 to push agent service 202.

Push agent service 202 can be further partitioned into a push renderingsystem that renders data in a form suitable for information sink 211 anda push distribution system that is specific to each information sink211. The push rendering systems and push distribution systems may bedistributed and scaled independently, or they may be implementedtogether in the push endpoint hosting service 208.

Pull hosting service 204 schedules a pull job from information source206 and gets data 205, which may be read as a stream from pull source206. Pull endpoint hosting service 204 downloads the data stream eitherin parallel or sequentially based on the configuration of the pullendpoint. In one embodiment, the pulled data 206 is then converted to aninternal SOAP-based protocol and pushed 209 out to the push agentservice 202.

Before pushing data 209, an address resolution is performed based on theaddress of information sink 211 to ensure that data 209 is sent to thecorrect push endpoint hosting service 208 that is responsible for theinformation sink 211. Structured overlay network 212 may maintain atable or database to assist in identify how the push endopoint hostingservices 208 are partitioned among the information sinks 211.

Data 209 may be transformed 213 to meet the specific protocol needs ofthe information sink 211. This protocol is published by the push agentservice 202. For every new information sink 211, push agent service 202defines a SOAP-based protocol, with appropriate SOAP headers andinterpretation, and creates a new runtime push endpoint hosting service208 replica for that protocol. Based on the transformation desired bythe user, the pull endpoint hosting service 204 may transform thedownloaded stream 205 into a protocol required by push agent service202. In other embodiments, a pipeline component may performtransformations between the pull agent and the push agent. For example,the pull agent may perform some basic transforms, and a dedicatedpipeline component between the pull agent and the push agent performsmore elaborate transformations. The push endpoint hosting service 208receives the incoming message 209 and translates the data 209 to theprotocol or format specific to the information sink 211.

FIG. 3 is a block diagram of a pull agent service 300 according to oneembodiment. The pull agent service 300 hosts a service—referred toherein as the pull endpoint hosting service 301—that hosts many pullsource 302. A pull source 302 describes a specific information source,and the pull agent service 300 pulls data from these sources 302. In oneembodiment, the pull endpoint hosting service 301 is a stateful servicethat allows for scaling of the pull agent service 300 in the form ofpull agent service replicas 301 over a structured overlay network 303.

The pull agent service has a gateway 304 that provides an external userinterface. The pull agent gateway 304 may provide a RepresentationalState Transfer (REST) interface in one embodiment. The gateway receivesconfiguration information identifying new information sources 302 andrequests to pull data from the information sources 302. Users enterrequests 305, such as GET, PUT, and DELETE requests, at pull agentgateway 304, which is the only means for users to operate on theendpoints to perform actions, such as get, create, update, or deleteoperations.

A pull agent management provider 306 is responsible for either servicingthe requests coming from gateway 304, such as GET requests, orforwarding the requests, such as PUT and DELETE requests, as a message307 to the appropriate pull endpoint hosting service 301. Pull agentmanagement provider 306 may assign a pull endpoint hosting service 301responsibility for a particular pull source 302. The pull endpointhosting service 301 stores 309 the endpoint configuration to a database308, such as a SQL database. Pull agent management provider 306 readsendpoint configuration information from database 308 directly when itreceives a request for the pull source 302 to identify which pullendpoint hosting service 301 is responsible for that source 302.

The pull endpoint hosting service 301 is responsible to poll the pullsource 302, which may be a poll to an external FTP server for example,and then download data 310 from the pull source 302. Once the contentsare downloaded from the pull source 302, the pull endpoint hostingservice 301 creates a message 311, such as an HTTP or SOAP message,using the data and passes the message 311 on to a push agent gateway312. The push agent gateway 312 address may be provided as part of thepull endpoint configuration information stored to database 308.

The pull agent service 300 is a scheduler that schedules many pullsources 302, which represent information sources from which data ispulled. The pull agent 300 is configured with a collection of pullsources 302 that are partitioned among the pull endpoint hostingservices 301. Each pull endpoint hosting service 301 is responsible forpulling data from a set of specific information sources 302. This may beconfigured by hashing on the pull information source configuration. Forexample, in the case of an FTP server, the FTP server name, server portand user name may be used by the pull endpoint hosting service 301 toconnect to the FTP service. In the case of another pull source 302 orinformation source, the hashing function uses a different set of inputs.The hashing logic may take co-location into account to optimize resourceusage on the information source 302. The pull agent service 300 may alsocheck for critical errors, such as authentication failure, during polland may shut down the poll if critical errors are found, or if too manynon-critical errors occur in a given poll or during a given timeinterval.

The structured overlay network 303 underneath the pull agent service 300helps in providing high levels of scalability and availability. Eachpull endpoint hosting service 301 is a stateful service, and thestructured overlay network 303 notifies if there is a change in thenetwork. For example, if there are one hundred pull sources 302 to pulldata from and there are four pull endpoint hosting services 301 on thestructured overlay network 303, then each pull endpoint hosting service301 pulls data from approximately twenty-five pull sources 302. One ormore machines or servers are used to host the pull endpoint hostingservices 301. A state change in the network occurs, for example, if oneof the hosting machines fails or if a new pull endpoint hosting service301 is added to handle the pull agent workload. The structured overlaynetwork 303 notifies each of the pull endpoint hosting service 301 ofthe change in how the pull sources 302 are partitioned. The pullendpoint hosting services 301 query the database 308, which stores theconfiguration data for all of the pull endpoints and how they areallocated to partitions. Each pull endpoint hosting service 301 fetchesthe set of pull sources 302 that it is responsible for scheduling andschedules jobs to pull data from the information sources 302.

In one embodiment, a pull endpoint or information has two parts: animplementation specific to the technology of the pull endpoint choice,such as FTP or a topic subscription; and a representation of the pullendpoint configuration, such as an address.

FIG. 4 illustrates three queues used to represent a single pull endpointaccording to one embodiment. In step 401, upon scheduling a pullendpoint the pull agent begins identifying work items. The work itemsare single-line descriptions or metadata that define the informationsought in the polls. The work items are stored to a pre-process queue402, which will contain a list of references to the actual informationsource identities. In the case of FTP, for example, the work items arefilenames.

Once work items are found and gathered, the pull agent beginsdownloading the data streams from the information sources in step 403,such as downloading files from an external FTP server. Based on theconcurrency count, the downloading may be done in parallel. The contentsof the data streams are queued in work item stream queue 404. When thedata streams are downloaded, an HTTP or SOAP message is created based onthe pull endpoint configuration to push the data out to a push agentservice in step 405. The SOAP messages are queued in work itempost-processing queue 406. Another thread will pick up these messagesand will post them to the push agent service. The post-processing queue406 will have an acknowledgement status for each data stream that wasposted to a push agent service. Upon acknowledgment from the push agentservice that the data has been pushed out successfully, the data may bedeleted from the information source in step 407. Alternatively, in thecase of a mail source, the data may be marked as read. This allows thedata pump to support ALO (At Least Once) semantics on pull/push.

Once a pull endpoint has exhausted all of the work items, it reschedulesthe next poll. Rescheduling may be based on internal monitoring oferrors and thresholds, for example. The following algorithm may be usedfor rescheduling in one embodiment:

-   -   1) If (ErrorCount/TotalItemCount) %>ErrorThreshold(70%) &&        ThrottledLevel==0        -   a) ThrottledLevel=1.        -   b) Set the ConcurrencyCount to 1.        -   c) Continue with next poll.    -   2) If (ErrorCount/TotalItemCount) %>ErrorThreshold(70%) &&        ThrottledLevel>0        -   a) If Throttledlevel==3 then call RequestShutdown else            continue        -   b) Increment the ThrottledLevel.        -   c) Double the poll interval.        -   d) Continue with poll.    -   3) If (ErrorCount/TotalItemCount) %<ErrorThreshold(70%) &&        ThrottledLevel>0        -   a) Check if the ThrottledLevel is 1, in which case set the            ConcurrencyCount to its original value.        -   b) If the ThrottledLevel is greater than 1, then decrease            poll interval by half        -   c) Decrement Throttledlevel.    -   4) Repeat steps 1-3 for InternalErrorCount unless shutdown of        endpoint is requested or throttling reaches zero.

FIG. 5 is a block diagram of a push agent service 500 according to oneembodiment. The push agent service follows a design that is symmetricalto the pull agent illustrated in FIG. 3. A collection of push agenthosting services 501 are hosted on a structured overlay network 502. Interms of availability and reliability, the push agent service 500 mayfollow the same model as pull agent service 300 to partition work. Thepush endpoint hosting service 501 may be broken into operations: therendering or formatting of content suitable to an information sink 503and the actual distribution of messages 504 to the information sink 503.Both of these operations may be partitioned and scaled out. In oneembodiment, the push endpoint hosting service 501 is a stateful servicethat allows for scaling of the push agent service 500 in the form ofpush agent service replicas 501 over a structured overlay network 502.

The push agent service 500 has a gateway 505 that provides an interfacefor endpoint request messages 506. The push agent gateway 505 mayprovide a REST interface in one embodiment. The gateway receivesconfiguration information identifying new information sinks 503 andrequests to push data to the information sink 503.

A push agent management provider 507 is responsible for either servicingthe requests coming from gateway 505 or forwarding the requests as amessage 508 to the appropriate push endpoint hosting service 501. Pushagent management provider 507 may assign a push endpoint hosting service501 responsibilities for a particular information sink 503. The pushendpoint hosting service 501 stores 509 the information sinkconfiguration to a database 510, which may be the same database 308 asused in the pull agent service. Push agent management provider 507 readsendpoint configuration information from database 510 directly when itreceives a request for the information sink 510 to identify which pushendpoint hosting service 501 is responsible for that information sink503.

The push agent service 500 is a reactive service that is triggered whena pull service sends a message to be transmitted. Push endpoints 501represent information sinks to which data is pushed. The push agent 500is configured with a collection of information sinks 503 that arepartitioned among the push endpoint hosting services 501. Each pushendpoint hosting service 501 is responsible for pushing data to a set ofspecific information sinks 503. This may be configured by hashing on thepush information source configuration. For example, in the case of anFTP server, the FTP server name, server port and user name may be usedby the push endpoint hosting service 501 to connect to the FTP service.In the case of another information sink 503, the hashing function uses adifferent set of inputs. The hashing logic may take co-location intoaccount to optimize resource usage and to preventing denial-of-serviceattack detection on the information sink 503. The push agent service 500may also check for critical errors, such as authentication failure, andsend an error message back to the pull agent or may shut down the pollif critical errors are found.

The structured overlay network 502 underneath the push agent service 500helps in providing high levels of scalability and availability. Eachpush endpoint hosting service 501 is a stateful service, and thestructured overlay network 502 notifies if there is a change in thenetwork. For example, if there are one hundred information sinks 503 topush data to and there are four push endpoint hosting services 501 onthe structured overlay network 502, then each push endpoint hostingservice 501 pushes data to approximately twenty-five information sinks503. One or more machines or servers are used to host the push endpointhosting services 501. A state change in the network occurs, for example,if one of the hosting machines fails or if a new push endpoint hostingservice 501 is added to handle the push agent workload. The structuredoverlay network 502 notifies each of the push endpoint hosting service301 of the change in how the information sinks 503 are partitioned. Thepush endpoint hosting services 501 query the database 510, which storesthe configuration data for all of the information sinks 503 and how theyare allocated to partitions. Each push endpoint hosting service 501fetches the set of information sinks 503 that it is responsible forscheduling and schedules jobs to push data to the information sinks 503.

In one embodiment, a push endpoint or information has two parts: animplementation specific to the technology of the information sinkchoice, such as FTP or a mobile device; and a representation of theinformation sink configuration, such as an address.

Upon receipt of a message, the push agent service retrieves the externalsink address and the endpoint configuration for that endpoint fromdatabase 510. An in-memory cache may be implemented to optimize on theconfiguration lookups. A handler for the transport is obtained based aconfiguration sub-class, and the message is dispatched to that handler.The handler uses the appropriate protocol library to send the messageover that transport.

Embodiments of the data pump disclosed and described herein may beimplemented using, for example, a general purpose computing device.Components of such a device may include, but are not limited to, varioushardware components, such as a processing unit, data storage, such as asystem memory, and a system bus that couples various system componentsincluding the data storage to the processing unit. The system bus may beany of several types of bus structures including a memory bus or memorycontroller, a peripheral bus, and a local bus using any of a variety ofbus architectures. By way of example, and not limitation, sucharchitectures include Industry Standard Architecture (ISA) bus, MicroChannel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus also known as Mezzanine bus.

The computing device may typically include a variety ofcomputer-readable media, such as any available media that can beaccessed by the computer and includes both volatile and nonvolatilemedia, and removable and non-removable media, but excludes propagatedsignals. By way of example, and not limitation, computer-readable mediamay comprise computer storage media and communication media. Computerstorage media includes volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information such as computer-readable instructions, data structures,program modules or other data. Computer storage media includes, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other medium which can be used tostore the desired information and which can accessed by the computer.Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above may also be included within the scope of computer-readablemedia. Computer-readable media may be embodied as a computer programproduct, such as software stored on computer storage media.

The data storage or system memory includes computer storage media in theform of volatile and/or nonvolatile memory such as read only memory(ROM) and random access memory (RAM). A basic input/output system(BIOS), containing the basic routines that help to transfer informationbetween elements within computer, such as during start-up, is typicallystored in ROM. RAM typically contains data and/or program modules thatare immediately accessible to and/or presently being operated on by aprocessing unit. By way of example, and not limitation, data storageholds an operating system, application programs, and other programmodules and program data.

Data storage may also include other removable/non-removable,volatile/nonvolatile computer storage media. By way of example only,data storage may be a hard disk drive that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive thatreads from or writes to a removable, nonvolatile magnetic disk, and anoptical disk drive that reads from or writes to a removable, nonvolatileoptical disk such as a CD ROM or other optical media. Otherremovable/non-removable, volatile/nonvolatile computer storage mediathat can be used in the exemplary operating environment include, but arenot limited to, magnetic tape cassettes, flash memory cards, digitalversatile disks, digital video tape, solid state RAM, solid state ROM,and the like. The drives and their associated computer storage mediaprovide storage of computer-readable instructions, data structures,program modules and other data for the computer.

A user may enter commands and information through a user interface orother input devices such as a tablet, electronic digitizer, amicrophone, keyboard, and/or pointing device, commonly referred to asmouse, trackball or touch pad. Other input devices may include ajoystick, game pad, satellite dish, scanner, or the like. Additionally,voice inputs, gesture inputs using hands or fingers, or other naturaluser interface (NUI) may also be used with the appropriate inputdevices, such as a microphone, camera, tablet, touch pad, glove, orother sensor. These and other input devices are often connected to theprocessing unit through a user input interface that is coupled to thesystem bus, but may be connected by other interface and bus structures,such as a parallel port, game port or a universal serial bus (USB). Amonitor or other type of display device may be also connected to thesystem bus via an interface, such as a video interface. The monitor mayalso be integrated with a touch-screen panel or the like. Note that themonitor and/or touch screen panel can be physically coupled to a housingin which the computing device is incorporated, such as in a tablet-typepersonal computer. In addition, computers such as the computing devicemay also include other peripheral output devices such as speakers andprinter, which may be connected through an output peripheral interfaceor the like.

The computer may operate in a networked or cloud-computing environmentusing logical connections to one or more remote devices, such as aremote computer. The remote computer may be a personal computer, aserver, a router, a network PC, a peer device or other common networknode, and typically includes many or all of the elements described aboverelative to the computer. The logical connections may include one ormore local area networks (LAN) and one or more wide area networks (WAN),but may also include other networks. Such networking environments arecommonplace in offices, enterprise-wide computer networks, intranets andthe Internet.

When used in a networked or cloud-computing environment, the computermay be connected to a public or private network through a networkinterface or adapter. Additionally, the service might be hosted in adata center, in multiple locations around the world for spatialefficiency and resilience. In some embodiments, a modem or other meansfor establishing communications over the network. The modem, which maybe internal or external, may be connected to the system bus via thenetwork interface or other appropriate mechanism. A wireless networkingcomponent such as comprising an interface and antenna may be coupledthrough a suitable device such as an access point or peer computer to anetwork. In a networked environment, program modules depicted relativeto the computer, or portions thereof, may be stored in the remote memorystorage device. It may be appreciated that the network connections shownare exemplary and other means of establishing a communications linkbetween the computers may be used.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

What is claimed is:
 1. A system for pushing data to a plurality of datasinks, the system comprising: a processor; and a memory coupled to theprocessor, the memory storing computer-readable instructions that, uponexecution by the processor, cause the system to: publish a protocolspecifying a data format supported by an assigned data sink of theplurality of data sinks, wherein the push service is tasked with pushingincoming data to the assigned data sink; receive a message indicatingincoming data is available for delivery to the assigned data sink;schedule delivery of the incoming data from a push job queue to theassigned data sink; and create a new runtime instance of the pushservice that transforms incoming data according to the protocolsupported by the assigned data sink.
 2. The system of claim 1, thememory storing additional computer-readable instructions that, uponexecution by the processor, cause the system to: accept an assignment ofan additional assigned data sink to the push service, wherein theassignment of the additional data sink serves to additionally task thepush service with pushing incoming data to the additional assigned datasink.
 3. The system of claim 1, wherein the incoming data is retrievedfrom a data source and placed in an incoming data queue by a pullservice component.
 4. The system of claim 2, wherein the additionalassignment of data sinks to the push service results from adjustments toa partitioning of the plurality of data sinks among a plurality of pushservice instances.
 5. A method for pushing data to a plurality of datasinks, the method comprising: providing a push service for distributingincoming data to the plurality of data sinks; publishing a protocolspecifying a data format supported by an assigned data sink of theplurality of data sinks, wherein the push service is tasked with pushingincoming data to the assigned data sink; receiving a message indicatingincoming data is available for delivery to the assigned data sink;scheduling delivery of the incoming data from a push job queue to theassigned data sink; and creating a new runtime instance of the pushservice that transforms incoming data according to the protocolsupported by the assigned data sink.
 6. The method of claim 5, furthercomprising: accepting an assignment of an additional assigned data sinkto the push service, wherein the assignment of the additional data sinkserves to additionally task the push service with pushing incoming datato the additional assigned data sink.
 7. The method of claim 5, whereinthe incoming data is retrieved from a data source and placed in anincoming data queue by a pull service.
 8. The method of claim 6, whereinthe additional assignment of data sinks to the push service results fromadjustments to a partitioning of the plurality of data sinks among aplurality of push service instances.
 9. A computer-readable storagememory device comprising instructions for pushing data to a plurality ofdata sinks, wherein the instructions, when executed, cause a processorto: provide a push service for distributing incoming data to theplurality of data sinks; publish a protocol specifying a data formatsupported by an assigned data sink of the plurality of data sinks,wherein the push service is tasked with pushing incoming data to theassigned data sink; receive a message indicating incoming data isavailable for delivery to the assigned data sink; schedule delivery ofthe incoming data from a push job queue to the assigned data sink; andcreate a new runtime instance of the push service that transformsincoming data according to the protocol supported by the assigned datasink.
 10. The computer-readable storage memory device of claim 9,further comprising instructions that, when executed, cause a processorto: accept an assignment of an additional assigned data sink to the pushservice, wherein the assignment of the additional data sink serves toadditionally task the push service with pushing incoming data to theadditional assigned data sink.
 11. The computer-readable storage memorydevice of claim 9, wherein the incoming data is retrieved from a datasource and placed in an incoming data queue by a pull service.
 12. Thecomputer-readable storage memory device of claim 10, wherein theadditional assignment of data sinks to the push service results fromadjustments to a partitioning of the plurality of data sinks among aplurality of push service instances.